Summary

Fix broken relative links in the GitHub Actions welcome workflow that produced invalid URLs in issue and PR welcome comments.

Motivation / Context

The welcome workflow used relative markdown links (e.g., ../blob/main/CONTRIBUTING.md, ../../labels) which don't resolve correctly when rendered in GitHub issue/PR comments. This caused new contributors to encounter broken links on their first interaction with the project.

Fixes: N/A
Related: N/A

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• Build/CI/tooling

Component(s) Affected

• CLI (cmd/aicr, pkg/cli)
• API server (cmd/aicrd, pkg/api, pkg/server)
• Recipe engine / data (pkg/recipe)
• Bundlers (pkg/bundler, pkg/component/*)
• Collectors / snapshotter (pkg/collector, pkg/snapshotter)
• Validator (pkg/validator)
• Core libraries (pkg/errors, pkg/k8s)
• Docs/examples (docs/, examples/)
• Other: GitHub Actions workflow (.github/workflows/welcome.yaml)

Implementation Notes

Replaced relative markdown links with fully-qualified GitHub URLs using context.repo.owner and context.repo.repo template variables. This ensures links resolve correctly regardless of where the comment is rendered. Changed the affected lines from single-quoted strings to template literals to enable variable interpolation.

Testing

# Verified the template literal syntax is valid JavaScript
# Confirmed the generated URLs match the expected format:
# https://github.com/NVIDIA/aicr/blob/main/CONTRIBUTING.md
# https://github.com/NVIDIA/aicr/labels
# https://github.com/NVIDIA/aicr/discussions

Risk Assessment

• Low — Isolated change, well-tested, easy to revert
• Medium — Touches multiple components or has broader impact
• High — Breaking change, affects critical paths, or complex rollout

Rollout notes: N/A

Checklist

• Tests pass locally (make test with -race)
• Linter passes (make lint)
• I did not skip/disable tests to make CI green
• I added/updated tests for new functionality
• I updated docs if user-facing behavior changed
• Changes follow existing patterns in the codebase
• Commits are cryptographically signed (git commit -S) — GPG signing info